Create 2020 roadmap 🛣️ #77

bobcatfish · 2020-02-14T19:00:18Z

I have put together a roadmap for 2020, which attempts to represent the
most requested of the features and issues that we've seen so far. I did
this by:

Reviewing the 2019 roadmap
Looking at the oldest and most commented on issues in Tekton Pipelines
and Tekton Triggers

I also added a section on Tekton's mission: this is the mission that
we've been using at Google when talking about Tekton - so this is a
great chance for anyone who is viewing Tekton differently to mention
their mission and vision so we can tweak it. Having more clarity around
what everyone is hoping accomplish with Tekton will make it easier to
make decisions around features, etc.

PTAL:

The governing board @abayer @vdemeester @afrittoli @imjasonh
Tekton Pipelines OWNERS @afrittoli @dibyom @sbwsg (and @imjasonh but he's on paternity leave so hopefully he ignores this! ❤️ )
Tekton Triggers OWNERS @iancoffey @vtereso @ncskier @wlynch
Tekton Catalog OWNERS @chmouel

And everyone else of course!!!!

Roadmaps for individual projects:

Pipelines: Update roadmap for 2020 🛣️ pipeline#2275
Triggers: Add 2020 roadmap 🛣️ triggers#498
Catalog: Add 2020 roadmap 🛣️ catalog#236
Dashabord: TBD, initial thoughts in Create 2020 roadmap 🛣️ #77 (comment)
CLI: TBD

vdemeester

We need to add cli, dashboard and operator roadmap docs in here too
/cc @chmouel @danielhelfand @nikhil-thomas @mnuttall @a-roberts @afrittoli

vdemeester · 2020-02-17T10:09:58Z

roadmap/README.md

@@ -0,0 +1,148 @@
+# Tekton Mission and Roadmap
+
+This doc describes Tekton's mission and the 2020 roadmap primarily


This doc should only be on Tekton's mission and main roadmap (aka as "what we want our components" to lead to) and have a ROADMAP document for the each project on their own.

Question is then, should the ROADMAP for the other project be here or on their own porject ?

ah kk! as long as we link from here maybe that's the way to go. i suppose on tekton.dev we can (hopefully) bring it all together!

vdemeester · 2020-02-17T10:11:17Z

roadmap/README.md

+
+Tekton's mission:
+
+  Be the industry-standard, cloud-native CI/CD platform components and ecosystem.


vdemeester · 2020-02-17T10:16:16Z

roadmap/README.md

+1. Beta for the remaining components
+1. Beta for [Tekton Triggers](#triggers)
+1. GA for both Tekton Pipelines and Tekton Triggers


We should be less specific on the beta on the tekton level. I would see something more like

We target a beta release for the core component earlier this year, leading to a full GA (1.0) release of a defined set of components

^^ we still need to discuss what we want to do for this, but my feeling is, as the project grows, we may want to have the main components released together and maybe share the same version number (easier to manage).

In a Tekton GA, I wanna see pipeline, triggers, cli and most likely the dashboard ; but in addition to that, I feel we should also target a versionned catalog that has a well defined process (validation, support, …)

Maybe we can get all the projects to release together, I'd like to weigh the pros and cons, I'm not 100% convinced - perhaps what I can put here can be more general, about making some decisions around this?

I do think it makes sense to be explicit about a beta release of Triggers tho for example.

vdemeester · 2020-02-17T10:16:41Z

roadmap/README.md

+As the project matures, we also require:
+
+1. A website that provides a good landing page for users (tekton.dev)
+1. Solid, high quality onboarding and documentation


This should be an item on its own, tekton.dev and documentation

vdemeester · 2020-02-17T10:18:15Z

roadmap/README.md

+  for [Catalog](#catalog) success
+- [Alternative Task Implementations](https://github.com/tektoncd/pipeline/issues/215)
+- [Local Execution](https://github.com/tektoncd/pipeline/issues/235)
+- Testing and debugging frameworks


ah! maybe I need to write up my thoughts here a bit more. I really like how projects like OPA come with their own built in support for testing (https://www.openpolicyagent.org/docs/latest/policy-testing/) and as @imjasonh and I hinted at super briefly in that russian doll talk, we could potentially use the entrypoint binary to expose some cool debugging support (e.g. letting users step through steps)

oh yeah also tektoncd/pipeline#1289

now we've also got tektoncd/pipeline#2069

@bobcatfish

@nikhil-thomas and I would be working on it. 😸

vdemeester · 2020-02-17T10:19:36Z

roadmap/README.md

+#### Task Interfaces and PipelineResources
+
+In alpha Tekton Pipelines, [`PipelineResources`](https://github.com/tektoncd/pipeline/issues/1673)
+were the interface between `Tasks` in a `Pipeline`: they were used for sharing typed
+data and variables between `Tasks`. This is being revisited and the feature has been
+deconstructed into:
+
+* `workspaces` - A way for a `Task` to declare data it needs and provides without
+  needing to know about the underlying mechanism used
+* `Task results` (aka "output params") - A way for a `Task` to provide values as outputs
+  which can be provided to downstream `Tasks`
+
+After adding these features we will once again reconsider the design of `PipelineResources`
+and decide what additional features, if any, we need.
+
+We will also need to decide how to continue to release and maintain the code that
+is used to build the images used by the existing `PipelineResources`:
+https://github.com/tektoncd/pipeline/tree/master/cmd.
+
+### SCM support
+
+SCM support in 2019 was handled by
+[the PullRequest Resource](https://github.com/tektoncd/pipeline/blob/master/docs/resources.md#pull-request-resource).
+However [we are revisting PipelineResources](#task-interfaces-and-pipelineresources),
+and likely this `PipelineResource` will become one or more `Tasks` in
+[the catalog](https://github.com/tektoncd/catalog) instead. Once that happens,
+we will need to make decisions about how to release and maintain the
+supporting code.
+
+* [GitHub App support](https://github.com/tektoncd/triggers/issues/189)
+* Support for more SCM providers
+
+### Results
+
+One of the benefits of [defining specifications around CI/CD](#mission-and-vision)
+is that we can start to create tools around inspecting what is moving through our
+Pipelienes. In 2019 we started some design work around a result storage system for
+Tekton, and we want to make progress on this in 2020:
+
+* Design reporting to results store: https://github.com/tektoncd/pipeline/issues/454
+* Snapshoting data for history + repeatability: https://github.com/tektoncd/pipeline/issues/279


This should be on a pipeline roadmap file 👼

Quick thought: I've been thinking of "results" as a new, totally separate project. e.g. i dont think using tekton pipelines should require using tekton results, kinda like tekton triggers. what do you think @vdemeester ?

ah 🙃 then it can be in the main "tekton" roadmap for now, and we'll update as we go 😝

vdemeester · 2020-02-17T10:21:02Z

roadmap/triggers.md

+In 2020 we would like to add missing features and then push for
+[Triggers to be Beta and later GA](#beta-and-ga):
+
+We are targetting improving the experience for both end users and operators:


Optional integration with knative maybe ?

Can you explain a bit more here? I'm still of the opinion that our best bet is to be as generic as possible

Hence "optional" in my comment 😛 An example would be : using a knative service to expose the EventListener instead of a standard K8S service. I should probably have written "optional integration with knative/serving" maybe 😝

I guess that could be under improved support for many EventListeners?

Im unclear of the value in exposing the listener via knative service rather than corev1.Service, and am curious about the improvement it would provide. I do love me some knative serving/eventing and use this combo with triggers regularly but feel like im missing the background.

@iancoffey not too much, just would like to be able to have a "scale-to-zero" service for event-listener

Maybe I can include this as "scale-to-zero EventListner"?

yeah works for me 😉

bobcatfish · 2020-02-17T14:09:33Z

I left some quick responses @vdemeester but I have a feeling I won't be returning to this this week - it's looking like a crazy one. If you want to make any changes to this directly plz do otherwise I'll make sure to get back to this as soon as I can (maybe next week? 🤞 )

a-roberts · 2020-02-17T14:20:17Z

@vdemeester for the Dashboard here's what I'm personally thinking would be useful to have, I'd like to get input from @mnuttall and @AlanGreene before we commit to anything in particular

Observability (which Trigger resulted in which PIpelineRun or TaskRun)
Currency (latest Pipeline and Trigger versions)
Performance through pagination and sorting (thanks to @afrittoli's dogfooding cluster we know we need this)
Visualisations (@AlanGreene has some excellent work in this area already)
Platforms (e.g. known to work on various clouds)
Improved test story, perhaps with Selenium - something that exercises our functionality against different versions (a colleague at IBM has been making good progress on this)
Staying on top of security issues and having a documented procedure (ideally this should be across the Tekton space)

mnuttall · 2020-02-26T17:01:38Z

@vdemeester Re @a-roberts' comments above on dashboard - we can't promise but Adam's list is very reasonable set of goals. Hopefully we'll make good progress on that list.

ncskier · 2020-02-26T22:06:08Z

roadmap/triggers.md

+
+* For end users:
+  * [Pluggable core interceptors](https://github.com/tektoncd/triggers/issues/271)
+  * [Increased expression support in TriggerBindings](https://github.com/tektoncd/triggers/issues/271)


This link is incorrect; it has the same link as the previous item. I think that it's supposed to link to issue 367: tektoncd/triggers#367

whoops, thanks for being thorough @ncskier ! :D

afrittoli · 2020-02-27T15:17:15Z

roadmap/README.md

+include.
+
+Features we don't have or aren't yet 100% satisfied with for "feature complete"
+Tekton:


Other ideas:

Looping: Support Task looping syntax inside Pipelines pipeline#2050, Add support for Task Step looping pipeline#2112

Alternative Task types - e.g. tasks with no underlying pod - for instance when waiting on input for an arbitrarily long time or so.

for the first, I agree but I know this is a somewhat contentious point!! I'm going to include it b/c between the 2 of us thats 2 people for it XD, maybe I'll include a caveat about deciding if we want to include looping

i think the second is covered by "Alternative Task Implementations" ?

In tektoncd/community#77 we started on a roadmap for 2020 for all of Tekton but folks pointed out it makes more sense to let each project's own roadmap live in the repo with them.

I have put together a roadmap for 2020, which attempts to represent the most requested of the features and issues that we've seen so far. I did this by: * [Reviewing the 2019 roadmap](https://docs.google.com/document/d/1zClmMJZU63kEDedjxTI99MCK-mXqm-Ym7PBfjMG5tQE/edit) * Looking at the oldest and most commented on issues in Tekton Pipelines and Tekton Triggers I also added a section on Tekton's mission: this is the mission that we've been using at Google when talking about Tekton - so this is a great chance for anyone who is viewing Tekton differently to mention their mission and vision so we can tweak it. Having more clarity around what everyone is hoping accomplish with Tekton will make it easier to make decisions around features, etc. Roadmaps for individual projects: * Pipelines: tektoncd/pipeline#2275 * Triggers: tektoncd/triggers#498 * Catalog: tektoncd/catalog#236 * Dashabord: TBD, initial thoughts in tektoncd#77 (comment) * CLI: TBD

bobcatfish · 2020-03-24T15:53:58Z

Okay I finally came back and tried to reply to everything and move roadmaps for each project into their repos:

Roadmaps for individual projects:

Pipelines: Update roadmap for 2020 🛣️ pipeline#2275
Triggers: Add 2020 roadmap 🛣️ triggers#498
Catalog: Add 2020 roadmap 🛣️ catalog#236
Dashabord: TBD <-- @a-roberts I'm assuming based on your short list above that you don't mind adding a roadmap.md to the dashboard project and linking here?
CLI: TBD

PTAL @vdemeester @afrittoli

In tektoncd/community#77 we started on a roadmap for 2020 for all of Tekton but folks pointed out it makes more sense to let each project's own roadmap live in the repo with them.

vdemeester

Two nits, otherwise looking good !

vdemeester · 2020-04-01T15:20:29Z

roadmap.md

+[does not include all Tekton Pipeline components](https://docs.google.com/document/d/1H8I2Rk4kLdQaR4mV0A71Qbk-1FxXFrmvisEAjLKT6H0/edit#heading=h.t0sc4hdrr5yq),
+we will work toward:
+
+1. Beta and GA for all Tekton Projects


Should we say all or the core component (and listing thoses: pipeline, triggers, cli, dashboard, ?)
An example is the new hub project, might not follow the exact same pattern (or any newly added project)

vdemeester · 2020-04-01T15:21:06Z

roadmap.md

+### Results
+
+One of the benefits of [defining specifications around CI/CD](#mission-and-vision)
+is that we can start to create tools around inspecting what is moving through our
+Pipelienes. In 2019 we started some design work around a result storage system for
+Tekton, and we want to make progress on this in 2020:
+
+* Design reporting to results store: https://github.com/tektoncd/pipeline/issues/454
+* Snapshoting data for history + repeatability: https://github.com/tektoncd/pipeline/issues/279


Isn't this pipeline specific ?

ah yeah that's true, I'll remove this

tekton-robot · 2020-04-01T15:21:25Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

~~OWNERS~~ [vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

In tektoncd/community#77 we started on a roadmap for 2020 for all of Tekton but folks pointed out it makes more sense to let each project's own roadmap live in the repo with them.

I have put together a roadmap for 2020, which attempts to represent the most requested of the features and issues that we've seen so far. I did this by: * [Reviewing the 2019 roadmap](https://docs.google.com/document/d/1zClmMJZU63kEDedjxTI99MCK-mXqm-Ym7PBfjMG5tQE/edit) * Looking at the oldest and most commented on issues in Tekton Pipelines and Tekton Triggers I also added a section on Tekton's mission: this is the mission that we've been using at Google when talking about Tekton - so this is a great chance for anyone who is viewing Tekton differently to mention their mission and vision so we can tweak it. Having more clarity around what everyone is hoping accomplish with Tekton will make it easier to make decisions around features, etc. Roadmaps for individual projects: * Pipelines: tektoncd/pipeline#2275 * Triggers: tektoncd/triggers#498 * Catalog: tektoncd/catalog#236 * Dashabord: TBD, initial thoughts in tektoncd#77 (comment) * CLI: TBD

In tektoncd/community#77 we started on a roadmap for 2020 for all of Tekton but folks pointed out it makes more sense to let each project's own roadmap live in the repo with them.

vdemeester · 2020-04-08T12:58:05Z

/lgtm

imjasonh · 2020-04-08T13:02:08Z

/lgtm 🎉

imjasonh · 2020-04-08T13:02:44Z

/lgtm 🎉

bobcatfish · 2020-04-08T13:03:56Z

Thanks all!!! :D

tekton-robot requested review from dlorenc and vdemeester February 14, 2020 19:00

googlebot added the cla: yes label Feb 14, 2020

tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 14, 2020

bobcatfish mentioned this pull request Feb 14, 2020

Create 2020 roadmap 🛣️ tektoncd/pipeline#1999

Closed

vdemeester requested changes Feb 17, 2020

View reviewed changes

tekton-robot requested review from a-roberts, afrittoli, chmouel, danielhelfand, mnuttall and nikhil-thomas February 17, 2020 10:21

bobcatfish mentioned this pull request Feb 21, 2020

Cloud Event Resource on pipeline completion tektoncd/pipeline#2053

Closed

bobcatfish force-pushed the add_2020_roadmap branch from 91fbe23 to 792c6a0 Compare February 21, 2020 13:32

ncskier reviewed Feb 26, 2020

View reviewed changes

afrittoli reviewed Feb 27, 2020

View reviewed changes

bobcatfish mentioned this pull request Mar 24, 2020

Add 2020 roadmap 🛣️ tektoncd/catalog#236

Merged

2 tasks

bobcatfish mentioned this pull request Mar 24, 2020

Add 2020 roadmap 🛣️ tektoncd/triggers#498

Merged

2 tasks

bobcatfish mentioned this pull request Mar 24, 2020

Update roadmap for 2020 🛣️ tektoncd/pipeline#2275

Merged

2 tasks

bobcatfish force-pushed the add_2020_roadmap branch from 792c6a0 to 5837ed8 Compare March 24, 2020 15:52

tekton-robot removed the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Mar 24, 2020

tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 24, 2020

a-roberts mentioned this pull request Mar 30, 2020

Create Dashboard roadmap tektoncd/dashboard#1211

Closed

3 tasks

vdemeester approved these changes Apr 1, 2020

View reviewed changes

tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 1, 2020

bobcatfish force-pushed the add_2020_roadmap branch from 5837ed8 to 44b9ccf Compare April 6, 2020 18:47

tekton-robot assigned vdemeester Apr 8, 2020

tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 8, 2020

tekton-robot merged commit 560b1a2 into tektoncd:master Apr 8, 2020

a-roberts mentioned this pull request Apr 8, 2020

Add Tekton Dashboard roadmap.md (and link to community one) tektoncd/dashboard#1266

Closed

		@@ -0,0 +1,148 @@
		# Tekton Mission and Roadmap

		This doc describes Tekton's mission and the 2020 roadmap primarily


		Tekton's mission:

		Be the industry-standard, cloud-native CI/CD platform components and ecosystem.

Create 2020 roadmap 🛣️ #77

Create 2020 roadmap 🛣️ #77

Conversation

bobcatfish commented Feb 14, 2020 • edited Loading

vdemeester left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

iancoffey Feb 21, 2020 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bobcatfish commented Feb 17, 2020

a-roberts commented Feb 17, 2020

mnuttall commented Feb 26, 2020

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bobcatfish commented Mar 24, 2020

vdemeester left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tekton-robot commented Apr 1, 2020

vdemeester commented Apr 8, 2020

imjasonh commented Apr 8, 2020

imjasonh commented Apr 8, 2020

bobcatfish commented Apr 8, 2020

bobcatfish commented Feb 14, 2020 •

edited

Loading

iancoffey Feb 21, 2020 •

edited

Loading